-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Swagger files for CLU 2022-03-01-preview #18067
Add Swagger files for CLU 2022-03-01-preview #18067
Conversation
Hi, @ChongTang Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vscswagger@microsoft.com |
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger Generation Artifacts
|
Hi @ChongTang, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi @JeffreyRichter, this PR adds CLU's swagger. We added it on top of the swagger of TA. Both services are under the same /language umbrella. However, there are two validation failures which I hope you can help us.
Thanks for your help. |
The board review issue: #17505 |
NewApiVersionRequired reason: |
Hi @tjprescott , this PR has the same [MISSING_APIS_IN_DEFAULT_TAG] failure in Avocado. I tried to add analyzeconversations.json in 2022-02-01-preview but it does not help. I want to add analyzeconversations.json only in 2022-03-01-preview. Really appreciate if you can help me out? My guess is that because "questionanswering.json" and "questionanswering-authoring.json" are in 2021-07-15-preview, but not in version after that. Is that correct? But the error message says: Looks like it's about analyzeconversations.json, so I am confused. Any help would be appreciated. |
Hi @weidongxu-microsoft or @tjprescott . This PR has the same MISSING_APIS_IN_DEFAULT_TAG issue. This PR merges CLU's 2022-03-01-preview version into a release/feature branch. Can you help us skip this check? Thanks! |
@ChongTang skip CI (due to false positive) will only happen before you are ready to merge. I don't think this PR is at this stage yet. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only concern blocking the PR is about some of the modelAsString: false
declarations. You should only specify false
if the model will only ever be input, or if you're 100% certain the discriminator will never change. Is that true for all instances of false
? Happy to flip to approve if so, though I had a few small nits as well but don't need to block the PR for those.
...n/cognitiveservices/data-plane/Language/preview/2022-03-01-preview/analyzeconversations.json
Show resolved
Hide resolved
...n/cognitiveservices/data-plane/Language/preview/2022-03-01-preview/analyzeconversations.json
Outdated
Show resolved
Hide resolved
...n/cognitiveservices/data-plane/Language/preview/2022-03-01-preview/analyzeconversations.json
Outdated
Show resolved
Hide resolved
...n/cognitiveservices/data-plane/Language/preview/2022-03-01-preview/analyzeconversations.json
Outdated
Show resolved
Hide resolved
...n/cognitiveservices/data-plane/Language/preview/2022-03-01-preview/analyzeconversations.json
Outdated
Show resolved
Hide resolved
...n/cognitiveservices/data-plane/Language/preview/2022-03-01-preview/analyzeconversations.json
Outdated
Show resolved
Hide resolved
...n/cognitiveservices/data-plane/Language/preview/2022-03-01-preview/analyzeconversations.json
Outdated
Show resolved
Hide resolved
...n/cognitiveservices/data-plane/Language/preview/2022-03-01-preview/analyzeconversations.json
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a couple that seem like they should be true
. Could you double check the following four, though?
These seem like they should be true. The discriminators - especially the first - seem like something that could easily change over time:
BaseResolution.resolutionKind
NumericRangeResolution.rangeKind
These very well could be immutable and never change, but might be good to double check assumptions:
DateTimeResolution.dateTimeSubKind
NumberResolution.numberKind
Apart from that, the changes look good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Heath! I resolve both "language" and "modelAsString" issues. I also searched in the file and resolved all occurrences. |
8d186bf
into
Azure:dev-cognitiveservices-Language-2022-03-01-preview
* Add Swagger files for CLU 2022-03-01-preview * Fix prettier errors * Fix sub id description * Try to fix the missing API error * Try to resolve the error of missing APIs in the default tag * Remove 2022-02-01 CLU files * Resolve comments * Resolve comments * Resolve more comments Co-authored-by: Chong Tang <chot@microsoft.com>
* Add Swagger files for CLU 2022-03-01-preview * Fix prettier errors * Fix sub id description * Try to fix the missing API error * Try to resolve the error of missing APIs in the default tag * Remove 2022-02-01 CLU files * Resolve comments * Resolve comments * Resolve more comments Co-authored-by: Chong Tang <chot@microsoft.com>
* Add Swagger files for CLU 2022-03-01-preview * Fix prettier errors * Fix sub id description * Try to fix the missing API error * Try to resolve the error of missing APIs in the default tag * Remove 2022-02-01 CLU files * Resolve comments * Resolve comments * Resolve more comments Co-authored-by: Chong Tang <chot@microsoft.com>
* Add Swagger files for CLU 2022-03-01-preview * Fix prettier errors * Fix sub id description * Try to fix the missing API error * Try to resolve the error of missing APIs in the default tag * Remove 2022-02-01 CLU files * Resolve comments * Resolve comments * Resolve more comments Co-authored-by: Chong Tang <chot@microsoft.com>
* Add Swagger files for CLU 2022-03-01-preview * Fix prettier errors * Fix sub id description * Try to fix the missing API error * Try to resolve the error of missing APIs in the default tag * Remove 2022-02-01 CLU files * Resolve comments * Resolve comments * Resolve more comments Co-authored-by: Chong Tang <chot@microsoft.com>
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.